In keeping with Microsoft's "pre-release" philosophy, this is a
"pre-release" postscript file viewer. It is a Win16 3.x program. 
The postscript interpreter is grafted onto my text/hex viewer.
I don't know whether it will stay on there for the final release
or not. And the help file is only partially completed.

Comments are welcome, preferably E-mail to CIS 73537,1203.

Notes on viewing Postscript files:

1) This is a Win16 program (my disk with NT on it crashed &
   has gone to the hospital). In fact, this version has not
   been tested on NT, since I don't have NT anymore.

2) LI only makes a first approximation attempt at processing
      a) text
      b) column positioning
      c) row positioning
      d) page ejects
   The 'interpretation' is based strictly on my examination of
   the files on the NT July & October disks. There are no guarantees
   that I'm doing it right. Positioning 'resolution' is character
   width and line height based on the viewed font. This doesn't
   work all that well. Fonts of 8-12pts seem to work best. 
   Row positioning is relative, not absolute. That is, I take 
   the difference between the previous 'Y' coordinate and the 
   current 'Y' coordinate & figure how many blank lines that is.
   'X' positioning is a little closer to absolute.

3) No character substitutions are performed.  Instead, where
   a character sub is found in the text, a binary 127 character
   is placed in the text. With an ANSI font, this looks like a
   black box on the screen, with the 'terminal' font, it looks
   like a superscripted pyramid. Printed with a True-type font,
   it looks like a little bullet.  I have found that the .C00 
   language files use substitution characters for quote marks 
   and minus signs a lot.

4) The .C00 language doc's use a lot of subscripted 'opt's. These
   will show up in the line since I don't do subscripts. 
   So you'll see a lot of:

   describes-an-optional-feature opt of-the-language.


5) I do not do 'page processing'. Text comes out in the order
   it's found in the file.  The 'cursor' can only move down
   and to the right. You'll see some tables that look
   like:

   item 1
   item 2
   item 3
                 item 4
                 item 5
                 item 6

   where if the file was printed on a native postscript printer,
   item 1 and item 4 would be on the same line. You may also see
   page headers at the bottom of the page, and the dots between
   table of contents entries and their page numbers at the end
   of the line instead of between the text and number - I don't 
   try to go back & put them where they belong.

6) If you want to print an 'interpreted' file, you will get best
   results with a true-type font and use 'match screen font' in
   the print dialog box with an 8-12pt font. Fixed spaced fonts 
   tend to run off of the right edge of the paper. You may need to
   experiment with font size, depending on the file you're
   viewing. 

7) If you want to automatically switch to postscript interpretation
   when you open one of the NT doc's, set up the extents under
   Options|File Types, or copy the LI.INI file in this archive
   to your \Windows directory.  If you're searching for text, or
   files containing specified text, it's best if you have the
   file types set up to be recognized as postscript. The View|Postscript
   menu item toggles between postscript interpretation and raw file
   output.